1
Easy2Siksha
GNDU Queson Paper - 2021
Bachelor of Computer Applicaon (BCA) 3rd Semester
DATABASE MANAGEMENT SYSTEM
Time Allowed – 3 Hours Maximum Marks-75
Note :- Aempt Five queson in all, selecng at least One queson from each secon . The
h queson may be aempted from any secon. All queson carry equal marks .
SECTION-A
1. What is Database Management System (DBMS)? What are the advantages of DBMS
over tradional le processing systems? Explain.
2. Discuss in detail the enty relaonship model with the help of suitable example.
SECTION-B
3. What do you mean by data security ? How database security is enforced in a database
system? Discuss in detail.
4. What is normalizaon? What is the need to normalize databases? What are its
advantages ? Explain giving examples.
SECTION-C
5. What is a cursor in SQL? Explain its type. How to create Implicit cursor in SQL ?
6.(a) List the dierence between DDL, DML and DCL.
(b) ACID properes of transacon.
2
Easy2Siksha
SECTION-D
7. Compare and evaluate between NoSQL, MySQL and Oracle.
8. What is HDFS? Explain the components of HDFS with a neat diagram.
GNDU Answer Paper - 2021
Bachelor of Computer Applicaon (BCA) 3rd Semester
DATABASE MANAGEMENT SYSTEM
SECTION-A
1. What is Database Management System (DBMS)? What are the advantages of DBMS
over tradional le processing systems? Explain.
Ans: Demysfying Database Management Systems (DBMS) and Their
Advantages
In the realm of data organizaon and management, Database Management Systems (DBMS)
emerge as powerful tools. They provide a structured and ecient way to store, retrieve, and
manage data. In this exploraon, we'll unravel the concept of DBMS in simple terms and
delve into the advantages they oer over tradional le processing systems.
What is a Database Management System (DBMS)?
At its core, a Database Management System, or DBMS, is like a digital librarian for
informaon. It's a soware suite designed to eciently manage databases, which are
organized collecons of data. Think of a database as a well-organized digital ling cabinet,
and the DBMS as the librarian who ensures that every piece of informaon is stored,
retrieved, and updated with precision.
Components of DBMS:
Data:
Data, in the context of a DBMS, refers to the informaon stored in the database. This could
be anything from customer details to inventory records.
3
Easy2Siksha
Database:
A database is a systemac collecon of data. It is structured in a way that facilitates easy
retrieval and manipulaon of informaon.
DBMS Soware:
The DBMS soware is the brain behind the database. It manages how data is stored,
retrieved, and updated. Popular DBMS soware includes MySQL, Oracle, and Microso SQL
Server.
Users:
Users interact with the DBMS to perform various operaons such as adding new data,
querying exisng data, and updang records.
Advantages of DBMS over Tradional File Processing Systems:
To truly grasp the signicance of DBMS, let's contrast it with tradional le processing
systems, which were prevalent before the advent of DBMS.
1. Data Integrity and Accuracy:
Tradional File Processing:
• In a le processing system, data is stored in separate les for dierent applicaons.
Each applicaon program has its own set of les.
• Ensuring data integrity and accuracy across mulple les can be challenging. Changes
made in one le may not be reected in others, leading to inconsistencies.
DBMS:
• DBMS enforces data integrity by applying constraints to the data. For example, it can
ensure that a customer's age is always a posive integer.
• It provides a centralized and standardized way to manage data, reducing the chances
of errors and inconsistencies.
2. Data Independence:
Tradional File Processing:
• Changes in the structure of a le, such as adding a new eld, oen require modifying
all programs that use that le.
• This lack of data independence makes the system rigid and suscepble to errors
during updates.
DBMS:
• DBMS provides data independence, separang the logical structure of the database
from its physical storage.
• Alteraons to the database structure don't impact the applicaon programs,
ensuring a more exible and adaptable system.
4
Easy2Siksha
3. Concurrent Access and Security:
Tradional File Processing:
• In le processing systems, concurrent access (mulple users accessing data
simultaneously) can lead to data corrupon and security issues.
• File-level security is oen challenging to implement eecvely.
DBMS:
• DBMS manages concurrent access through features like transacon management,
ensuring data consistency even with mulple users.
• It provides robust security mechanisms, allowing access control at various levels,
from the enre database down to specic data rows.
4. Data Redundancy and Eciency:
Tradional File Processing:
• Data redundancy, where the same data is duplicated in mulple les, is common in
le processing systems.
• This redundancy not only consumes more storage space but also makes updates and
maintenance complex.
DBMS:
• DBMS minimizes data redundancy through normalizaon, a process that organizes
data to eliminate duplicate informaon.
• Reducing redundancy not only saves storage but also enhances eciency in terms of
data retrieval and maintenance.
5. Data Query and Reporng:
Tradional File Processing:
• Wring complex queries and generang reports in a le processing system oen
involves extensive programming eorts.
• Retrieving specic informaon may require navigang through mulple les.
DBMS:
• DBMS simplies data querying through Structured Query Language (SQL), a powerful
and standardized language for interacng with databases.
• It facilitates easy retrieval of specic data, and reporng becomes more
straighorward with SQL queries.
6. Scalability and Flexibility:
Tradional File Processing:
• Expanding or modifying a le processing system to accommodate changing business
requirements can be cumbersome.
5
Easy2Siksha
• Scaling up the system oen involves extensive redevelopment.
DBMS:
• DBMS provides scalability as databases can be easily expanded to accommodate
growing data needs.
• It oers exibility to adapt to evolving business requirements without major
overhauls.
7. Data Relaonships and Integrity Constraints:
Tradional File Processing:
• Maintaining relaonships between data in dierent les requires manual eort and
programming logic.
• Enforcing integrity constraints can be challenging, leading to data quality issues.
DBMS:
• DBMS facilitates the establishment and maintenance of relaonships between tables
through keys.
• It enforces integrity constraints, ensuring that data adheres to predened rules,
enhancing overall data quality.
Conclusion:
In essence, a Database Management System serves as a guardian of informaon, oering a
structured and ecient approach to handling data. Its advantages over tradional le
processing systems, ranging from data integrity and independence to enhanced security and
scalability, make it an indispensable tool in the modern digital landscape.
The transion from le processing systems to DBMS represents a paradigm shi in how
organizaons manage and leverage their data. With DBMS, businesses gain not only
eciency and accuracy in data handling but also the agility to adapt to the dynamic
demands of today's informaon-driven world. In simple terms, DBMS acts as a reliable and
intelligent custodian, ensuring that data remains organized, accessible, and secure, laying
the foundaon for eecve decision-making and innovaon.
2. Discuss in detail the enty relaonship model with the help of suitable example.
Ans: Understanding the Enty-Relaonship Model: A Simple Guide
In the realm of database design, the Enty-Relaonship (ER) model stands as a powerful tool
for visualizing and dening the structure of a database. This model, based on enes,
aributes, and relaonships, provides a clear and intuive representaon of how data is
6
Easy2Siksha
organized and connected. Let's explore the Enty-Relaonship model in simple terms, using
an example to illustrate its key concepts.
Basics of the Enty-Relaonship Model:
Enes:
• An enty is a real-world object or concept with a disnct identy that can be
uniquely idened.
• Examples of enes include a person, place, thing, or event. In a database, enes
are oen represented as tables.
Aributes:
• Aributes describe the properes or characteriscs of enes.
• For a "Person" enty, aributes might include "Name," "Age," and "Address."
Relaonships:
• Relaonships illustrate how enes are connected or associated with each other.
• A "Works for" relaonship might connect a "Person" enty with an "Organizaon"
enty.
Example: Employee Management System
Let's consider a simple example of an Employee Management System to understand the
Enty-Relaonship model beer.
Enes:
• Employee:
o Aributes:
o EmployeeID (Primary Key)
o Name
o Posion
o DateOfBirth
Example Data:
• (101, John Doe, Manager, 1990-05-15)
• (102, Jane Smith, Developer, 1988-09-22)
Department:
• Aributes:
o DepartmentID (Primary Key)
o DepartmentName
Example Data:
o (D001, HR)
o (D002, IT)
7
Easy2Siksha
Relaonships:
Works for:
• Connects "Employee" to "Department."
• Indicates which employee works for which department.
Example Data:
o (John Doe works for HR)
o (Jane Smith works for IT)
Manages:
• Connects "Employee" to "Employee."
• Indicates the manager-subordinate relaonship within the organizaon.
• Example Data:
o (John Doe manages Jane Smith)
Cardinality in Relaonships:
Cardinality denes the number of instances of one enty that are related to the number of
instances of another enty.
1. One-to-One (1:1):
Example: Each employee has one and only one desk, and each desk belongs to only
one employee.
2. One-to-Many (1:N):
Example: Each department has many employees, but each employee works in only
one department.
3. Many-to-One (N:1):
Example: Many employees work in one department, but a department has only one
manager.
4. Many-to-Many (N:N):
Example: Many employees can aend many training sessions, and each training
session can have many employees.
Creang an Enty-Relaonship Diagram (ERD):
An ERD is a visual representaon of the database structure using enes, aributes, and
relaonships. Let's create a simplied ERD for our Employee Management System example.
Employee Management System ERD:
In this ERD:
• The rectangles represent enes (Employee and Department).
• The ovals represent aributes within each enty.
• The lines connecng enes illustrate relaonships (Works for and Manages).
• The crow's feet notaon (three lines) indicates a "Many" side of the relaonship.
8
Easy2Siksha
Advantages of the Enty-Relaonship Model:
1. Clarity and Visualizaon:
The ER model provides a clear and visual representaon of the database structure,
making it easier for stakeholders to understand.
2. Database Design:
It serves as a foundaonal tool for designing databases, helping in the creaon of
tables and relaonships.
3. Communicaon:
Database designers, developers, and stakeholders can use the ER model as a
common language to discuss and communicate database requirements.
4. Normalizaon:
The ER model supports the normalizaon process, ensuring data is organized
eciently and avoiding redundancy.
Limitaons of the Enty-Relaonship Model:
• Simplicity Oversimplicaon:
While simplicity is an advantage, it can somemes oversimplify complex relaonships
or business rules.
• Real-World Complexity:
Represenng certain real-world scenarios, especially complex ones, might require
addional modeling techniques.
• Evoluon Challenges:
Adapng the model to changes in requirements may pose challenges, especially if
the inial design lacks exibility.
Conclusion:
In essence, the Enty-Relaonship model provides a conceptual framework for designing
and understanding databases. Through enes, aributes, and relaonships, it oers a way
to organize and visualize the intricate web of data within an organizaon. By translang real-
world scenarios into a structured model, the ER model serves as a foundaonal tool in the
world of database design, ensuring that data is not just stored but also interconnected in a
meaningful and ecient manner.
SECTION-B
3. What do you mean by data security ? How database security is enforced in a database
system? Discuss in detail.
Ans: Understanding Data Security: Safeguarding Digital Assets
9
Easy2Siksha
Data security is a crical aspect of the digital landscape, encompassing measures and
pracces that aim to protect sensive informaon from unauthorized access, disclosure,
alteraon, or destrucon. It involves ensuring the condenality, integrity, and availability of
data, safeguarding it against potenal threats and vulnerabilies. In the realm of database
systems, where vast amounts of valuable informaon reside, database security plays a
pivotal role in forfying the fortress around digital assets.
What is Data Security?
Data security is the pracce of implemenng protecve measures to ensure the safety and
privacy of digital informaon. It involves safeguarding data from various threats, including
unauthorized access, data breaches, cyberaacks, and accidental loss.
Key Components of Data Security:
Condenality:
• Denion: Keeping informaon accessible only to authorized individuals or systems.
• Implementaon: Encrypon, access controls, and secure transmission methods help
maintain condenality.
Integrity:
• Denion: Ensuring that data remains accurate and unaltered during storage,
processing, or transmission.
• Implementaon: Hash funcons, digital signatures, and version control mechanisms
help maintain data integrity.
Availability:
• Denion: Ensuring that authorized users can access data when needed.
• Implementaon: Redundancy, backup systems, and disaster recovery plans
contribute to data availability.
Database Security: Forfying the Data Fortress
In the realm of database systems, where vast repositories of structured informaon reside,
database security becomes paramount. It involves protecng databases from unauthorized
access, data breaches, and malicious acvies. Let's explore how database security is
enforced, focusing on key measures and strategies.
1. Access Controls:
Simple Explanaon: Access controls determine who has permission to access, modify, or
delete data within a database.
Implementaon: Role-based access control (RBAC), user authencaon, and authorizaon
mechanisms limit access to authorized personnel based on their roles and responsibilies.
10
Easy2Siksha
2. Encrypon:
• Simple Explanaon: Encrypon transforms readable data into a coded format,
making it unreadable without the appropriate decrypon key.
• Implementaon: Database encrypon methods protect sensive data, both at rest
(stored) and during transmission, prevenng unauthorized access.
3. Authencaon Mechanisms:
• Simple Explanaon: Authencaon veries the identy of individuals accessing the
database.
• Implementaon: Usernames, passwords, biometrics, and mul-factor authencaon
(MFA) systems ensure that only authorized users can gain access.
4. Audit Trails:
• Simple Explanaon: Audit trails record and track acvies within a database,
allowing administrators to monitor user acons.
• Implementaon: Logging mechanisms capture informaon such as login aempts,
data modicaons, and system changes, aiding in forensic analysis and compliance.
5. Data Masking and Redacon:
• Simple Explanaon: Data masking and redacon hide specic porons of sensive
informaon to protect privacy.
• Implementaon: Techniques like paral masking or replacing sensive data with
conal values in non-producon environments ensure that real data is not exposed.
6. Database Acvity Monitoring (DAM):
• Simple Explanaon: DAM involves connuous monitoring of database acvies to
detect and respond to suspicious behavior.
• Implementaon: Real-me analysis of database events and anomalies helps idenfy
potenal security threats and vulnerabilies.
7. Firewalls and Network Security:
• Simple Explanaon: Firewalls and network security measures protect databases
from external threats by controlling trac and securing network connecons.
• Implementaon: Network rewalls, intrusion detecon/prevenon systems, and
virtual private networks (VPNs) create barriers against unauthorized access.
8. Regular Soware Updates and Patch Management:
• Simple Explanaon: Keeping database soware up-to-date ensures that known
vulnerabilies are patched, reducing the risk of exploitaon.
• Implementaon: Regularly applying soware updates, security patches, and xes
provided by database vendors enhances system security.
11
Easy2Siksha
9. Backup and Recovery Plans:
• Simple Explanaon: Backup and recovery plans involve creang duplicate copies of
databases to restore informaon in case of data loss or system failures.
• Implementaon: Regularly scheduled backups, o-site storage, and recovery
procedures contribute to data resilience.
10. Security Training and Awareness:
Simple Explanaon: Educang users and administrators about security best pracces and
potenal threats enhances overall security posture.
Implementaon: Training programs, awareness campaigns, and simulated phishing exercises
contribute to a security-conscious organizaonal culture.
Challenges in Database Security:
While various measures contribute to enhancing database security, challenges persist in this
ever-evolving landscape.
Human Factor:
• Challenge: Users may inadvertently compromise security through weak passwords,
sharing credenals, or falling vicm to phishing aacks.
• Migaon: Ongoing security awareness training helps users recognize and migate
potenal threats.
Zero-Day Vulnerabilies:
• Challenge: Emerging security vulnerabilies that are unknown or unpatched can be
exploited by aackers.
• Migaon: Regular monitoring, threat intelligence, and prompt applicaon of
patches help address zero-day vulnerabilies.
Insider Threats:
• Challenge: Authorized users with malicious intent pose a signicant risk to data
security.
• Migaon: Role-based access controls, least privilege principles, and monitoring for
anomalous behavior help detect and prevent insider threats.
Future Trends in Database Security:
As technology connues to advance, several trends are shaping the future of database
security:
Blockchain Integraon:
• Trend: Incorporang blockchain technology for secure and tamper-resistant record-
keeping.
12
Easy2Siksha
• Impact: Enhances data integrity and transparency, parcularly in scenarios where
trust is crical.
Arcial Intelligence (AI) and Machine Learning (ML):
• Trend: Leveraging AI and ML for proacve threat detecon and automated response.
• Impact: Enables quicker idencaon of paerns and anomalies, improving the
speed and eciency of security measures.
Homomorphic Encrypon:
• Trend: Exploring homomorphic encrypon to perform computaons on encrypted
data without decrypon.
• Impact: Enhances privacy by allowing secure data processing without exposing
sensive informaon.
Conclusion:
In a world driven by data, the security of databases is a foundaonal element in protecng
sensive informaon. Database security involves a mul-faceted approach, incorporang
access controls, encrypon, monitoring, and user educaon. As technology evolves, the
landscape of threats and vulnerabilies connues to change, necessitang adapve and
proacve security measures.
By implemenng robust security pracces, organizaons can forfy their databases against
potenal breaches, ensuring the condenality, integrity, and availability of their digital
assets. As we move forward, staying vigilant, embracing emerging technologies, and
fostering a security-aware culture will be crucial in the ongoing quest to safeguard valuable
digital informaon.
4. What is normalizaon? What is the need to normalize databases? What are its
advantages? Explain giving examples.
Ans: Simplifying Normalizaon: Ensuring Database Harmony
In the realm of databases, normalizaon is a crucial concept that ensures data is organized
eciently, avoiding redundancy and maintaining harmony within the database structure.
This process plays a pivotal role in creang well-structured databases, opmizing storage,
and enhancing data integrity. Let's explore what normalizaon is, why it is needed, its
advantages, and delve into praccal examples to demysfy this essenal database design
concept.
Understanding Normalizaon:
What is Normalizaon?
Normalizaon is a systemac process in database design aimed at minimizing redundancy
and dependency by organizing data into well-structured tables. It involves breaking down
13
Easy2Siksha
large tables into smaller, related tables, ensuring that each table represents a single logical
enty. The goal is to reduce data anomalies, enhance data integrity, and simplify the
management of informaon.
The Need for Normalizaon:
1. Avoiding Redundancy:
• Redundancy occurs when the same data is stored in mulple places, leading to
ineciency and increased storage requirements.
• Normalizaon eliminates redundancy by organizing data logically and storing it in
one place, reducing the risk of inconsistencies.
2. Minimizing Update Anomalies:
• Update anomalies occur when updang data in one place but not in others, leading
to inconsistencies.
• Normalizaon helps minimize update anomalies by ensuring that updates only need
to be made in one place.
3. Enhancing Data Integrity:
• Data integrity refers to the accuracy and consistency of data within a database.
• Normalizaon improves data integrity by structuring data in a way that prevents
contradicons and ensures accurate representaons.
4. Simplifying Queries:
• Normalized databases make queries simpler and more ecient.
• Since data is organized logically, queries can be formulated without the need to
navigate through unnecessary informaon.
Advantages of Normalizaon:
1. Reduced Redundancy:
By eliminang redundancy, normalizaon reduces storage requirements and ensures that
data modicaons are made in one place, avoiding inconsistencies.
2. Improved Data Integrity:
Normalizaon enhances data integrity by prevenng contradictory informaon and ensuring
accurate and consistent data representaon.
3. Simplied Maintenance:
• Managing and maintaining a normalized database is more straighorward.
• Changes or updates are localized, reducing the chances of errors and making the
database more adaptable to evolving requirements.
14
Easy2Siksha
4. Ecient Queries:
Normalized databases simplify query formulaon, making them more ecient and ensuring
that the required data is easily retrievable.
Understanding Normalizaon Levels:
Normalizaon is typically carried out in mulple stages or levels, each addressing specic
types of dependencies. The most common normalizaon levels are represented by normal
forms, denoted as 1NF, 2NF, 3NF, BCNF, and somemes 4NF and 5NF.
1. First Normal Form (1NF):
• In 1NF, data is organized into tables, and each aribute contains atomic values.
• Atomic values are indivisible, ensuring that each cell in the table contains only one
piece of data.
2. Second Normal Form (2NF):
• 2NF builds on 1NF by eliminang paral dependencies.
• It ensures that non-key aributes are fully funconally dependent on the primary
key, and tables are free from paral dependency.
3. Third Normal Form (3NF):
• 3NF further renes the normalizaon process by removing transive dependencies.
• It ensures that non-key aributes are not dependent on other non-key aributes
within the same table.
4. Boyce-Codd Normal Form (BCNF):
• BCNF focuses on addressing anomalies related to super keys.
• It ensures that no non-prime aribute is dependent on a super key, providing
addional normalizaon.
Praccal Examples of Normalizaon:
Let's consider a simple scenario: a library database with informaon about books and
authors.
1. Unnormalized Data:
A single table containing informaon about books and authors may result in redundancy and
inconsistency.
BookID
Title
Author
Genre
1
"Book1"
"Author1"
"Ficon"
2
"Book2"
"Author2"
"Non-Ficon"
15
Easy2Siksha
BookID
Title
Author
Genre
3
"Book3"
"Author1"
"Ficon"
2. First Normal Form (1NF):
Organizing data into atomic values.
BookID
Title
Author
Genre
1
"Book1"
"Author1"
"Ficon"
2
"Book2"
"Author2"
"Non-Ficon"
3
"Book3"
"Author1"
"Ficon"
3. Second Normal Form (2NF):
Ensuring no paral dependencies.
Books Table:
BookID
Title
AuthorID
Genre
1
"Book1"
1
"Ficon"
2
"Book2"
2
"Non-Ficon"
3
"Book3"
1
"Ficon"
Authors Table:
AuthorID
Author
1
"Author1"
2
"Author2"
4. Third Normal Form (3NF):
Eliminang transive dependencies.
Books Table:
BookID
Title
AuthorID
GenreID
1
"Book1"
1
1
2
"Book2"
2
2
16
Easy2Siksha
BookID
Title
AuthorID
GenreID
3
"Book3"
1
1
Authors Table:
AuthorID
Author
1
"Author1"
2
"Author2"
Genres Table:
GenreID
Genre
1
"Ficon"
2
"Non-Ficon"
5. Boyce-Codd Normal Form (BCNF):
• Ensuring no non-prime aribute is dependent on a super key.
• BCNF can be considered in this context, ensuring that there are no issues related to
super keys.
Conclusion:
Normalizaon, though inially might seem complex, is essenally a way of organizing data
within databases to avoid redundancy and maintain data integrity. By breaking down large
tables into smaller, related ones, normalizaon ensures that each piece of data is stored in
one place, reducing the chances of inconsistencies and making databases more ecient.
In praccal terms, normalizaon involves a step-by-step process, starng from ensuring
atomic values to eliminang transive dependencies and beyond. This process not only
organizes data logically but also simplies queries, updates, and maintenance.
So, the next me you encounter the term "normalizaon" in the context of databases,
remember that it's all about ensuring harmony, eciency, and accuracy within the intricate
world of digital informaon storage and retrieval.
17
Easy2Siksha
SECTION-C
5. What is a cursor in SQL? Explain its type. How to create Implicit cursor in SQL ?
Ans: Understanding Cursors in SQL: Navigang Through Database Rows
In the world of databases and SQL (Structured Query Language), a cursor is a powerful tool
that allows users to traverse through the rows of a result set. Think of a cursor as a virtual
pointer or a mechanism that facilitates the sequenal processing of data within a database.
Let's unravel the concept of cursors, explore their types, and understand how to create an
implicit cursor in SQL in simple terms.
What is a Cursor in SQL?
In SQL, a cursor is essenally a mechanism that enables the traversal of rows returned by a
SQL query. It acts as a pointer, poinng to a specic row within a result set. Cursors are
parcularly useful when dealing with mulple rows of data, allowing users to move through
the dataset one row at a me. They provide a way to interact with the results of a query
programmacally.
Types of Cursors in SQL:
Cursors in SQL can be classied into two main types: Implicit Cursors and Explicit Cursors.
1. Implicit Cursors:
Descripon:
o Implicit cursors are automacally created by the database management system
(DBMS) to handle the result sets of SQL queries.
o They are convenient for simple queries where manual cursor management is not
necessary.
Behavior:
o Implicit cursors are automacally opened when a SQL statement is executed, and
they are automacally closed when the statement is complete.
o They are read-only and provide limited control over the result set.
Use Cases:
o Implicit cursors are suitable for scenarios where straighorward access to query
results is sucient, and no addional cursor manipulaon is required.
2. Explicit Cursors:
Descripon:
o Explicit cursors are created by users when more control over the result set is needed.
18
Easy2Siksha
o They oer the ability to fetch and process rows individually, providing greater
exibility.
Behavior:
o Users need to declare and dene explicit cursors before using them.
o Cursors need to be explicitly opened, and users have control over when to fetch rows
and when to close the cursor.
Use Cases:
Explicit cursors are benecial in situaons where a ner level of control over the result set is
required, such as iterang through rows condionally or updang data.
How to Create an Implicit Cursor in SQL:
Creang an implicit cursor in SQL involves execung a SQL query, and the database
automacally handles the result set using the implicit cursor. Let's break down the process
into simple steps:
Step 1: Wring a SQL Query:
Example:
SELECT employee_id, employee_name, salary FROM employees WHERE department_id =
10;
In this example, we are selecng employee details from the "employees" table where the
department ID is 10.
Step 2: Execung the SQL Query:
Execuon:
The SQL query is executed, and the database generates an implicit cursor to handle the
result set.
Step 3: Fetching Rows:
Fetching:
o The implicit cursor automacally fetches the rows of the result set.
o Users can access the values of each column in the fetched row.
19
Easy2Siksha
In this PL/SQL block, the implicit cursor fetches rows from the "employees" table for the
specied department ID (10). The fetched values are then stored in variables for further
processing.
Step 4: Closing the Cursor:
Implicit Closure:
The implicit cursor is automacally closed when the loop or block completes execuon.
Advantages of Implicit Cursors:
Simplicity:
o Implicit cursors are easy to use and require minimal code for basic result set
processing.
o They are suitable for straighorward queries where manual cursor management is
unnecessary.
Automac Handling:
• The database automacally opens, fetches, and closes implicit cursors, reducing the
burden on users.
20
Easy2Siksha
Read-Only Nature:
• Implicit cursors are inherently read-only, making them suitable for scenarios where
modicaon of data is not required.
Limitaons of Implicit Cursors:
1. Limited Control:
Users have limited control over the behavior of implicit cursors, as they are
automacally managed by the database.
2. Read-Only:
Implicit cursors are primarily designed for read-only operaons, and users cannot
perform updates or deleons on the result set directly.
3. Simplicity vs. Flexibility Trade-o:
While implicit cursors are simple to use, they may lack the exibility required for
complex result set manipulaons.
Conclusion:
In summary, cursors in SQL, whether implicit or explicit, serve as vital tools for navigang
through result sets obtained from queries. Implicit cursors, automacally managed by the
database, oer simplicity and ease of use for scenarios where basic result set processing is
sucient. Users can leverage implicit cursors to fetch rows, access column values, and
perform simple operaons without the need for extensive manual cursor management.
Understanding how to create and use implicit cursors provides a foundaonal knowledge of
SQL cursor funconality, empowering users to interact with and process database data
eecvely. As users progress in their SQL journey, they may explore explicit cursors for more
ne-grained control and advanced result set manipulaon.
6.(a) List the dierence between DDL, DML and DCL.
Ans: Simplied Explanaon: Understanding the Dierences between DDL, DML, and DCL
In the world of databases, managing and manipulang data involves various operaons,
each serving a disnct purpose. DDL (Data Denion Language), DML (Data Manipulaon
Language), and DCL (Data Control Language) are key components in database management
systems. Let's break down the dierences between these three in simple terms.
Data Denion Language (DDL):
1. Denion:
• DDL deals with the structure and denion of the database objects.
• It focuses on creang, altering, and deleng database structures like tables, indexes,
and schemas.
21
Easy2Siksha
2. Key Operaons:
CREATE:
• DDL uses the CREATE operaon to build new database objects. For example, creang
a new table involves specifying its columns and data types.
ALTER:
• ALTER is used to modify the structure of exisng database objects. This can include
adding or removing columns from a table.
DROP:
• DROP is employed to delete or remove a database object enrely. For instance,
dropping a table removes it from the database.
3. Example:
Suppose you want to create a new table called "Employees" with columns for "EmployeeID,"
"FirstName," and "LastName." In DDL, you'd use the CREATE TABLE statement.
Data Manipulaon Language (DML):
1. Denion:
• DML focuses on the manipulaon and processing of data within the database.
• It deals with operaons like inserng, updang, retrieving, and deleng data stored
in the database.
2. Key Operaons:
INSERT:
• The INSERT operaon is used to add new records or rows to a table. For instance,
adding a new employee's informaon to the "Employees" table.
UPDATE:
• UPDATE modies exisng data in a table. This might involve changing the last name
of an employee.
22
Easy2Siksha
SELECT:
• SELECT retrieves data from one or more tables. It's used to query the database and
fetch specic informaon.
DELETE:
• DELETE removes records from a table. For example, deleng an employee who is no
longer with the company.
3. Example:
Let's say you want to insert a new employee into the "Employees" table:
Data Control Language (DCL):
1. Denion:
• DCL is concerned with access control and permissions within a database.
• It manages who can access the database, perform specic operaons, or manipulate
data.
2. Key Operaons:
GRANT:
• GRANT provides specic privileges to users or roles. It allows them to perform certain
acons, like SELECT or UPDATE, on specied database objects.
REVOKE:
• REVOKE takes away previously granted privileges. It restricts users from performing
specic operaons.
Example:
If you want to grant SELECT permission on the "Employees" table to a user named "Analyst,"
you would use:
Dierences Summarized:
1. Focus:
23
Easy2Siksha
• DDL:
Focuses on dening and managing the structure of the database.
• DML:
Concentrates on manipulang and processing the data stored in the database.
• DCL:
Deals with controlling access and permissions within the database.
2. Operaons:
• DDL:
Involves operaons like CREATE, ALTER, and DROP for database objects.
• DML:
Involves operaons like INSERT, UPDATE, SELECT, and DELETE for data manipulaon.
• DCL:
Uses operaons like GRANT and REVOKE to control access and permissions.
3. Examples:
• DDL:
Creang a new table or altering the structure of an exisng one.
• DML:
Inserng new data, updang exisng records, selecng informaon, or deleng data.
• DCL:
Granng or revoking specic privileges to control user access.
Conclusion:
In essence, DDL, DML, and DCL serve disnct purposes in the realm of databases. DDL
denes the structure, DML manipulates the data, and DCL controls access and permissions.
Understanding these fundamental dierences is key to eciently managing and interacng
with databases. Whether you're creang tables, inserng data, or granng permissions, each
language plays a vital role in ensuring the smooth funconing of a database management
system.
(b) ACID properes of transacon.
Ans:ACID Properes of Transacons: A Simple Guide to Data Reliability
In the realm of databases and informaon systems, ensuring the integrity and reliability of
data is paramount. This is where the ACID properes of transacons come into play. ACID,
an acronym for Atomicity, Consistency, Isolaon, and Durability, outlines a set of principles
that dene the reliability and correctness of database transacons. Let's unravel the
complexies and understand these ACID properes .
1. Atomicity:
24
Easy2Siksha
What is Atomicity?
Atomicity revolves around the idea of treang a transacon as an atomic unit. In simple
terms, atomicity ensures that a transacon is like a single, indivisible operaon. It either
happens enrely or not at all.
Example:
Imagine transferring money from one bank account to another. If this is a transacon,
atomicity ensures that either the enre transfer happens, and both accounts are updated, or
none of it happens, maintaining the consistency of the data.
Why is Atomicity Important?
Atomicity guarantees that even if a system crashes or encounters an error mid-transacon, it
won't leave the database in an inconsistent state. The transacon is rolled back to its inial
state if it fails at any point.
2. Consistency:
What is Consistency?
Consistency refers to the idea that a transacon brings the database from one consistent
state to another. In other words, the execuon of a transacon ensures that the integrity
constraints dened in the database are not violated.
Example:
• Consider a database that stores informaon about students and their courses. If a
transacon involves adding a new course for a student, consistency ensures that
aer the transacon, the database sll adheres to rules like each student having a
unique ID or having valid course codes.
Why is Consistency Important?
Consistency ensures that a transacon doesn't compromise the overall correctness and logic
of the database. It prevents scenarios where data becomes contradictory or violates
predened rules.
3. Isolaon:
What is Isolaon?
Isolaon ensures that the execuon of one transacon is independent and doesn't interfere
with the execuon of other transacons. Each transacon is isolated from others unl it is
commied.
Example:
• Imagine two people booking ights simultaneously. Isolaon ensures that one
person's booking process doesn't aect the other's. They both proceed
independently unl they reach the commit stage.
25
Easy2Siksha
Why is Isolaon Important?
Isolaon prevents transacons from interfering with each other, avoiding scenarios where
one transacon reads data that another transacon is in the process of modifying. This
prevents data inconsistency and ensures the reliability of the transacons.
4. Durability:
What is Durability?
Durability is about the lasng eect of a commied transacon. Once a transacon is
commied, its eects are permanent and survive system failures, crashes, or reboots.
Example:
• If a user updates their email address in an online plaorm and the transacon is
commied, durability ensures that even if the system crashes aerward, the change
to the email address remains intact when the system recovers.
Why is Durability Important?
Durability guarantees the persistence of data changes. It ensures that once a user receives a
conrmaon that a transacon is successful, they can trust that the changes will persist,
even in the face of unexpected events like power outages or system crashes.
The ACID Properes Working Together:
Let's understand how these ACID properes work together through a real-world analogy:
Analogy: Baking a Cake
Atomicity:
• Imagine baking a cake. Either all the ingredients come together, and the cake is baked
successfully, or something goes wrong, and the enre process is aborted. It's like the
baking process is atomic; it happens enrely or not at all.
Consistency:
For our analogy, consistency would mean ensuring that the ingredients used are the right
ones, the oven temperature is correct, and the cake follows the recipe. It's about
maintaining the integrity and correctness of the cake-making process.
Isolaon:
Consider two people baking cakes side by side. Isolaon ensures that the ingredients one
person is using don't interfere with the other person's process. They can each follow their
recipe independently without aecng the other's outcome.
Durability:
26
Easy2Siksha
Once the cake is baked and taken out of the oven, durability ensures that the cake doesn't
vanish or change if someone accidentally knocks over the mixing bowl. The baked cake
persists, and its state remains unchanged.
ACID Properes in Acon: A Database Scenario
Now, let's apply these concepts to a database scenario:
1. Atomicity:
Imagine a database transacon that involves transferring money between two
accounts. If the transfer process fails at any point (maybe due to a system crash),
atomicity ensures that the money is neither deducted from one account nor added
to the other.
2. Consistency:
Consistency ensures that the transacon doesn't violate any rules, such as ensuring
that the sum of all account balances remains constant. If the transacon would lead
to an inconsistency (e.g., negave account balance), it is rolled back.
3. Isolaon:
If mulple transacons are happening simultaneously, isolaon ensures that one
transacon's changes are not visible to others unl the transacon is commied. This
prevents scenarios where one transacon reads parally updated data from another
transacon.
4. Durability:
Once the transacon is commied, durability ensures that the changes persist. Even
if there's a system crash aer the transfer is complete, when the system recovers, the
database will reect the successful money transfer.
5. Challenges and Trade-os:
While the ACID properes provide a solid foundaon for data reliability,
implemenng them might come with trade-os in terms of performance and
scalability. In scenarios where systems require high-speed, massive concurrent
transacons, developers might opt for a more relaxed set of principles known as the
BASE model (Basically Available, So state, Eventually consistent).
The BASE model sacrices some of the strict guarantees of ACID in favor of improved
performance and scalability. In distributed systems and NoSQL databases, BASE
principles might be more suitable, especially in scenarios where instant consistency is
not crical.
Conclusion:
In the dynamic landscape of databases and informaon systems, the ACID properes of
transacons stand as pillars of reliability. They ensure that database transacons maintain
their integrity, consistency, and reliability even in the face of unexpected events or errors.
Understanding the ACID properes is fundamental for developers, database administrators,
and anyone involved in designing systems that handle crical data. These principles provide
a framework for building robust and dependable systems, ensuring that data remains
accurate and trustworthy throughout its lifecycle. Whether in the world of banking, e-
27
Easy2Siksha
commerce, or any domain relying on databases, the ACID properes are a cornerstone in the
pursuit of data reliability and integrity.
SECTION-D
7. Compare and evaluate between NoSQL, MySQL and Oracle.
Ans: Unveiling the World of Databases: NoSQL, MySQL, and Oracle
In the realm of databases, dierent systems cater to various needs, and three prominent
players are NoSQL, MySQL, and Oracle. Each has its strengths and weaknesses, making them
suitable for dierent scenarios. Let's embark on a journey to simplify and compare these
databases, exploring their features, use cases, and overall performance.
NoSQL: Embracing Flexibility
What is NoSQL?
NoSQL, which stands for "Not Only SQL," is a database management system designed to
handle unstructured or semi-structured data. Unlike tradional relaonal databases, NoSQL
databases are schema-less, allowing for more exibility in handling diverse data types.
Key Features of NoSQL:
• Schema-less Design:
NoSQL databases don't enforce a rigid schema, enabling developers to insert data
without predened structures. This exibility is advantageous in scenarios where
data structures may evolve over me.
• Horizontal Scalability:
NoSQL databases excel in horizontal scaling, distribung data across mulple servers
or clusters. This makes them suitable for handling large volumes of data and
achieving high performance.
• Variety of Data Models:
NoSQL databases support various data models, including document-oriented (like
MongoDB), key-value pairs (like Redis), column-family stores, and graph databases.
Each model caters to specic use cases.
• Quick Development:
NoSQL databases are oen preferred in agile development environments due to their
exibility. Developers can quickly adapt the database structure to accommodate
changing applicaon requirements.
28
Easy2Siksha
Use Cases for NoSQL:
1. Big Data Applicaons:
NoSQL databases are well-suited for handling the massive volumes of data generated
by big data applicaons, where scalability and quick access to unstructured data are
crucial.
2. Real-me Applicaons:
Applicaons requiring real-me processing, such as chat applicaons, gaming, and
social media plaorms, benet from NoSQL databases' ability to handle dynamic and
unpredictable data loads.
3. Content Management Systems:
NoSQL databases are oen used in content management systems where content
structures can vary, and quick updates or changes are common.
MySQL: The Relaonal Workhorse
What is MySQL?
• MySQL is a widely used open-source relaonal database management system
(RDBMS) known for its reliability, performance, and ease of use. It adheres to the SQL
(Structured Query Language) standard and operates on a relaonal model.
Key Features of MySQL:
1. ACID Compliance:
MySQL follows the ACID (Atomicity, Consistency, Isolaon, Durability) properes,
ensuring the integrity and consistency of transacons. This makes it suitable for
applicaons requiring strict data integrity.
2. Ease of Use:
MySQL's popularity lies in its ease of use. It comes with a robust set of tools and
documentaon, making it accessible to developers and administrators with varying
levels of experse.
3. Community Support:
Being open source, MySQL has a vast and acve community that contributes to its
development and provides support. This community-driven approach ensures
connuous improvement and reliability.
4. Data Security:
MySQL oers features like user access control, encrypon, and authencaon
mechanisms to ensure data security. It is well-suited for applicaons handling
sensive informaon.
Use Cases for MySQL:
1. Web Applicaons:
MySQL is widely used in web applicaons, including content management systems,
e-commerce plaorms, and blogging plaorms, where relaonal data storage and
retrieval are fundamental.
29
Easy2Siksha
2. Business Applicaons:
Business applicaons, such as CRM (Customer Relaonship Management) systems
and ERP (Enterprise Resource Planning) systems, benet from MySQL's reliability and
support for complex queries.
3. Data Warehousing:
MySQL can be employed in data warehousing scenarios where the relaonal model is
essenal for organizing and querying large datasets.
Oracle: Power and Scalability
What is Oracle?
Oracle Database, oen referred to simply as Oracle, is a powerful and feature-rich relaonal
database management system developed by Oracle Corporaon. It is known for its
robustness, scalability, and extensive set of enterprise-level features.
Key Features of Oracle:
1. High Performance:
Oracle is designed for high-performance data processing and retrieval. It incorporates
advanced query opmizaon techniques, caching mechanisms, and indexing to
ensure swi access to data.
2. Scalability and Availability:
Oracle excels in scalability, allowing organizaons to handle increasing data volumes
by distribung data across mulple servers. It also provides features like Oracle Real
Applicaon Clusters (RAC) for high availability.
3. Advanced Security Features:
Oracle oers a comprehensive set of security features, including ne-grained access
control, encrypon, and auding. These features make it suitable for applicaons
with stringent security requirements.
4. Multenant Architecture:
With its multenant architecture, Oracle allows organizaons to manage mulple
databases as a single container database. This provides resource isolaon and easier
management of database instances.
Use Cases for Oracle:
Enterprise-level Applicaons:
Oracle is widely used in enterprise-level applicaons, including large-scale ERP systems, data
warehouses, and nancial systems, where scalability, reliability, and advanced features are
paramount.
Crical Business Processes:
Applicaons handling crical business processes, such as online transacon processing
(OLTP) systems, leverage Oracle's robustness and transacon management capabilies.
30
Easy2Siksha
Data Warehousing and Analycs:
Oracle Database is a popular choice for data warehousing and analycal applicaons. It
supports complex queries, aggregaons, and reporng, making it suitable for business
intelligence scenarios.
A Comparave Overview:
1. Data Model:
• NoSQL: Supports various data models, including document-oriented, key-value pairs,
column-family, and graph databases.
• MySQL: Relaonal database with a structured, tabular data model.
• Oracle: Relaonal database with a structured, tabular data model.
2. Scalability:
• NoSQL: Excellent horizontal scalability, suitable for handling large volumes of data
across mulple servers.
• MySQL: Scalable, but scaling oen involves vercal scaling (adding more resources to
a single server).
• Oracle: Scalable with advanced features like Oracle RAC for horizontal scalability.
3. Flexibility:
• NoSQL: Highly exible due to its schema-less design, allowing dynamic changes to
data structures.
• MySQL: Flexible, but changes to the schema may require careful planning.
• Oracle: Requires careful schema design, and changes may involve more planning and
administraon.
4. ACID Compliance:
• NoSQL: ACID compliance depends on the specic NoSQL database. Some may
priorize eventual consistency over strict ACID compliance.
• MySQL: ACID compliant, ensuring transaconal integrity.
• Oracle: ACID compliant with strong support for transacon management.
5. Community and Support:
`Diverse community support, with specic communies for each NoSQL database type.
• MySQL: Extensive community support, with a wealth of documentaon and forums.
• Oracle: Strong community and ocial support, especially for enterprise users.
6. Use Cases:
• NoSQL: Ideal for scenarios with unstructured or evolving data, such as big data
applicaons and real-me processing.
31
Easy2Siksha
• MySQL: Well-suited for tradional relaonal database use cases, including web
applicaons, business applicaons, and data warehousing.
• Oracle: Preferred for enterprise-level applicaons, crical business processes, and
scenarios requiring advanced features and scalability.
Conclusion: Choosing the Right Database for the Job
In the dynamic world of databases, the choice between NoSQL, MySQL, and Oracle depends
on the specic requirements of the applicaon or system. NoSQL databases oer exibility
and scalability for dynamic data structures and large datasets. MySQL, with its reliability and
ease of use, is a go-to choice for many tradional applicaons. Oracle, with its enterprise-
level features, scalability, and robustness, is oen selected for mission-crical applicaons.
Ulmately, the key lies in understanding the unique needs of the project, considering factors
like data structure, scalability requirements, and the level of enterprise features needed.
Whether embracing the exibility of NoSQL, the reliability of MySQL, or the power of Oracle,
each database system brings its own strengths to the table, shaping the digital landscape
and enabling diverse applicaons to thrive.
8. What is HDFS? Explain the components of HDFS with a neat diagram.
Ans: Understanding HDFS: Simplifying Big Data Storage
In the realm of big data, managing vast amounts of informaon eciently is a formidable
challenge. Hadoop Distributed File System (HDFS) emerges as a soluon, providing a robust
framework for distributed storage and processing of enormous datasets. Let's demysfy
HDFS, exploring its components through simple terms and a clear diagram.
What is HDFS?
HDFS, short for Hadoop Distributed File System, is a distributed le system designed to store
and manage large volumes of data across a cluster of commodity hardware. It is a key
component of the Apache Hadoop framework, which is widely used for processing and
analyzing big data.
Core Principles of HDFS:
Distributed Storage:
• HDFS divides large datasets into smaller blocks, typically 128 MB or 256 MB in size.
• These blocks are distributed across mulple nodes in a cluster, enabling parallel
processing.
32
Easy2Siksha
Fault Tolerance:
• HDFS is designed for fault tolerance, meaning it can withstand the failure of
individual nodes without losing data.
• It achieves fault tolerance through data replicaon, storing mulple copies of each
block on dierent nodes.
Scalability:
• HDFS scales horizontally, allowing organizaons to expand their storage capacity by
adding more nodes to the cluster.
• This scalability is crucial for accommodang the ever-growing volumes of big data.
Components of HDFS:
To understand HDFS beer, let's explore its key components, each playing a unique role in
the storage and retrieval of data.
1. NameNode:
• The NameNode is the central component of HDFS and serves as the master server. Its
primary funcons include:
Metadata Management:
• The NameNode manages metadata about les and directories in the le system.
• It keeps track of the structure of the le system, including informaon about each
le's locaon and the associated data blocks.
Namespace and Permissions:
• The NameNode is responsible for maintaining the namespace, dening the hierarchy
of directories and les.
• It also manages permissions and access control for les and directories.
Heartbeat and Block Report:
• DataNodes, the worker nodes in the cluster, regularly send heartbeat signals and
block reports to the NameNode.
• The heartbeat signals indicate that a DataNode is alive, and block reports provide
informaon about the blocks stored on that DataNode.
2. DataNode:
DataNodes are worker nodes responsible for storing and managing data blocks. Key features
of DataNodes include:
Block Storage:
• DataNodes store actual data blocks and provide read and write operaons for these
blocks.
33
Easy2Siksha
• Each DataNode manages the blocks that are replicated across the cluster.
Heartbeat and Block Report:
• As menoned earlier, DataNodes regularly send heartbeat signals to the NameNode
to indicate their availability.
• Block reports provide informaon about the blocks stored on that parcular
DataNode.
Data Replicaon:
• DataNodes handle the replicaon of data blocks to ensure fault tolerance.
• If a DataNode fails or becomes unavailable, the replicated blocks can be retrieved
from other nodes.
3. Secondary NameNode:
Despite its name, the Secondary NameNode is not a backup for the primary NameNode.
Instead, it performs periodic checkpoints to enhance the eciency of the NameNode. Its
roles include:
Checkpoint Creaon:
• The Secondary NameNode creates periodic checkpoints by merging the edit log and
fsimage les of the NameNode.
• This process helps reduce the recovery me in case the NameNode fails.
Edit Log and FsImage:
• The edit log records every change made to the le system, while the fsimage is a
snapshot of the le system's metadata.
• The Secondary NameNode merges these les to create a new fsimage, prevenng
the edit log from growing indenitely.
4. Client:
Clients interact with the HDFS cluster to read or write data. Key responsibilies of clients
include:
Data Read and Write:
• Clients can read and write data to HDFS by interacng with the NameNode and
DataNodes.
• They submit requests for data operaons, and the HDFS architecture ensures the
distributed storage and retrieval of data.
Metadata Operaons:
Clients communicate with the NameNode for metadata operaons, such as lisng
directories, obtaining le informaon, and managing permissions.
34
Easy2Siksha
HDFS Architecture Diagram:
To visualize the interacon between these components, let's explore a simplied HDFS
architecture diagram:
Data Flow in HDFS:
Now, let's follow the data ow in a typical HDFS operaon:
Write Operaon:
• A client requests to write data to HDFS, and the NameNode provides informaon
about the available DataNodes.
• The client sends the data to a selected DataNode, which then replicates the data
across other DataNodes for fault tolerance.
• The client receives acknowledgment upon successful storage.
Read Operaon:
• A client requests to read data from HDFS, and the NameNode provides the locaons
of the data blocks.
• The client retrieves the data directly from the selected DataNodes, leveraging parallel
processing for faster read operaons.
Advantages of HDFS:
1. Scalability:
HDFS scales horizontally, allowing organizaons to expand storage capacity by adding
more nodes to the cluster.
2. Fault Tolerance:
Through data replicaon and the ability to recover from node failures, HDFS ensures
the integrity of data even in the face of hardware issues.
3. Parallel Processing:
35
Easy2Siksha
HDFS facilitates parallel processing by storing data in distributed blocks, enabling
faster read and write operaons.
4. Cost-Eecve:
HDFS is designed to run on commodity hardware, making it a cost-eecve soluon
for organizaons dealing with large datasets.
Challenges and Consideraons:
1. Small File Problem:
HDFS is opmized for large les, and the storage of numerous small les can lead to
ineciencies.
2. Write Once, Read Many (WORM):
HDFS is designed for scenarios where data is wrien once and read mulple mes.
Frequent updates to exisng les may not be as ecient.
3. Not Suitable for All Workloads:
While HDFS excels in storing and processing large datasets, it may not be the best t
for all types of workloads, such as those requiring real-me processing.
Conclusion:
HDFS stands as a foundaonal component in the landscape of big data, providing a reliable
and scalable soluon for storing and processing massive datasets. By distribung data across
a cluster of nodes and ensuring fault tolerance, HDFS addresses the challenges posed by the
volume and complexity of modern data. As organizaons connue to embrace the era of big
data, the role of HDFS remains pivotal in enabling ecient data management and analysis.
Note: This Answer Paper is totally Solved by Ai (Arcial Intelligence) So if You nd Any Error Or Mistake .
Give us a Feedback related Error , We will Denitely Try To solve this Problem Or Error.
